Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce the wasmtime::EqRef type #9285

Merged
merged 3 commits into from
Sep 19, 2024

Conversation

fitzgen
Copy link
Member

@fitzgen fitzgen commented Sep 19, 2024

This commit introduces the wasmtime::EqRef type, which corresponds to Wasm's (ref eq) type, and statically represents Wasm references that can be tested for equality. This is primarily for use with Func::typed-style APIs.

This commit introduces the `wasmtime::EqRef` type, which corresponds to Wasm's
`(ref eq)` type, and statically represents Wasm references that can be tested
for equality.
@fitzgen fitzgen requested a review from a team as a code owner September 19, 2024 19:28
@fitzgen fitzgen requested review from alexcrichton and removed request for a team September 19, 2024 19:28
@@ -1445,7 +1452,8 @@ impl Func {
/// | `(ref nofunc)` | `NoFunc` |
/// | `v128` | `V128` on `x86-64` and `aarch64` only |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While you're here mind removing this clause about aarch64/x86_64? (it's available on all platforms now)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I had no other comments so gonna go ahead and merge

@alexcrichton alexcrichton added this pull request to the merge queue Sep 19, 2024
Merged via the queue into bytecodealliance:main with commit c16414f Sep 19, 2024
39 checks passed
@fitzgen fitzgen deleted the eqref-api-type branch September 19, 2024 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants